Skip to content

Conversation

@suojae
Copy link
Contributor

@suojae suojae commented Jan 19, 2025

This PR addresses the CI issues reported in the previous PR.
The CI failures appear to be environment-specific.

Related Issue

@suojae suojae force-pushed the feature/add-dispose-method branch 3 times, most recently from 21ba02a to eb224c4 Compare January 19, 2025 20:39
@simolus3
Copy link
Owner

Looks like you also need to run dart format.

@suojae suojae force-pushed the feature/add-dispose-method branch from eb224c4 to 62df868 Compare January 20, 2025 00:57
@suojae
Copy link
Contributor Author

suojae commented Jan 26, 2025

Thanks! I’ve addressed the formatting issue as suggested. Please let me know if there’s anything else I can help with or any additional changes you'd like me to make. ☺️

@simolus3
Copy link
Owner

simolus3 commented Feb 2, 2025

Thanks, and sorry for being slow to respond. We still need to investigate the crash in the test (see the failing github action). It looks like we might close the database twice somehow, or fail to unregister a native callback. That shouldn't be possible (and might be a bug in package:sqlite3). But it's weird that these changes surface that issue.

@suojae
Copy link
Contributor Author

suojae commented Feb 3, 2025

Thanks! I’ll take a look at sqlite3 and see if I can spot anything related to the crash. I'll let you know if I find anything useful :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unclosed SQLite Tracker Database in DatabaseTracker

2 participants